Spin up a working backend in seconds.
Stateful endpoints with JSON storage. Always-on, curlable, and predictable—no servers or databases to manage.
Old way: mock servers, local DBs, schema migrations, flaky fixtures. ReqRes way: create an endpoint, save state, share a URL, and keep shipping.
Need a demo before stand-up? Launch it in 30 seconds.
When product asks to see the flow tomorrow, you can’t wait on backend bandwidth. Choose a template or upload a screenshot and ReqRes spins up live endpoints with realistic data—so the conversation stays on the experience, not the infrastructure.
from screenshot to shareable API
product-ready templates
iterations without backend tickets
🎯 From idea to curlable endpoint in seconds
No boilerplate, no local servers, no schema migrations. Build a working, stateful API you can hit from curl, tests, or the browser.
🚀 Create or pick a template
Start from a template or a simple JSON shape. One click gives you a real endpoint with predictable responses.
💾 Save state without a database
Persist JSON instantly—no servers or DB migrations. Your data stays consistent between reviews and tests.
🎨 Ship and share live endpoints
Hand PMs, QA, and agents a real URL backed by rate limits and analytics—no more mock server disclaimers.
Free to try • No credit card required • Instant results
Clarity, speed, and fewer blockers
Spin up stateful APIs without boilerplate, keep JSON stable between reviews, and ship without waiting on a server.
Ship demos the same day
Turn a request into a curlable endpoint in seconds. Keep data stable across reviews without running a local server.
- •Create endpoints in seconds—no Postman mocks or boilerplate.
- •Persistent JSON so reviewers see the same data every time.
- •Predictable responses you can curl, script, or drop into tests.
Keep QA & automation honest
Model edge cases without rebuilding fixtures. Serve predictable JSON to CI and automation.
- •Custom endpoints with the exact payloads your suites expect.
- •Read/write/manage keys so only the right people mutate data.
- •Always-on endpoints; no local DB or fixture drift.
Production-ready when you need it
Keep the same endpoints from prototype to launch: rate limits, uptime, analytics, and key-level control included.
- •99.99% uptime infra, Cloudflare at the edge.
- •Per-key rate limits and analytics to see real behavior.
- •Access controls by key; upgrade to SLAs and private endpoints.
⚡ See how teams go from idea to live API in minutes
This is the exact flow front-end squads use when the PM says “Can we show it tomorrow?”—fast, persistent, and realistic enough for real feedback.
1. Create the endpoint your UI expects
Drop in the path your component already calls and use the API key from your ReqRes workspace. No waiting on backend reviews or staging deploys.
fetch('https://reqres.in/api/users', {
headers: {
'x-api-key': 'YOUR_API_KEY'
}
})
.then(res => res.json())
.then(data => console.log(data))
2. Share a production-like response
ReqRes returns structured JSON immediately, ready for QA to automate against and for stakeholders to experience live.
{
"data": [
{
"id": 1,
"email": "[email protected]",
"first_name": "George",
"last_name": "Bluth"
}
]
}
Create a workspace, generate your key in seconds, upgrade to Pro when you need persistence
⚡ Keep product velocity high after the first demo
Upgrade when your team needs persistent data, collaboration controls, and analytics that survive real usage. ReqRes becomes the shared backend your PMs, QA, and engineers can trust.
🚀 Upgrade nowChoose the plan that matches your job-to-be-done
Join the front-end squads, agencies, and QA teams already using ReqRes to deliver on aggressive timelines.
Cancel anytime
Infrastructure your stakeholders can trust
When you walk execs through a demo, it has to work. ReqRes runs on Cloudflare and already powers billions of monthly requests, so your “prototype” performs like production.
Unique Visitors (30d)
Requests (30d)
Data Served (30d)
🚀 Join the teams shipping faster
Upgrade to Pro nowFAQ
- What is a persistent backend API?A persistent backend API stores and manages your data across requests. ReqRes lets you create stateful endpoints that save data with POST/PUT/DELETE operations, perfect for building MVPs and prototypes without a traditional backend. Your data persists in JSON document storage with automatic CRUD endpoints.
- How do custom endpoints work?Custom endpoints let you create your own API endpoints with custom JSON responses. Define the path, method, and response data—perfect for testing and mock APIs. Higher endpoint limits available on Premium.
- What are the different API key types? ReqRes offers three API key permission levels: read-only (GET only), read/write (GET, POST, PUT, PATCH), and manage (includes DELETE). This gives you fine‑grained control over access.
- What is the Data Explorer?The Data Explorer is a web interface that lets you view, search, and manage all your persisted data. You can see all stored objects keyed by ID and path, with advanced filtering and real-time analytics—available on Pro and Premium plans.
- Can I use ReqRes for production? Yes. Pro and Premium provide persistent storage and infrastructure suitable for production workloads. SLA available on Enterprise.
- What are the starter plan limits? Every workspace key has starter limits for the core fake data APIs. Upgrade to Pro for persistence, custom endpoints, and higher limits.
It's all in the details
Hosted on Cloudflare
Which means 99.9% Uptime SLA. All you need is the base URL, and you're away:
https://reqres.in/api/
The API is CORS enabled, so you can make requests right from
the browser, no matter what domain, or even from somewhere
like CodeSandbox or StackBlitz. Include your workspace API
key via the x-api-key header on every call for
consistent responses.
Language agnostic
A generic API that conforms to REST principles and accepts a
content type of application/json
Any endpoint that contains "<resource>" can be substituted with anything you supply, ie. "products", "accounts", etc..the API will just respond with various Pantone colours.
Give it a try
🔥 Love what you see?
Unlock unlimited requests, custom endpoints, and priority support
🚀 See plansAnnual billing available
No setup fees • Cancel anytime
Getting started
Use your workspace API key in every request header; it keeps responses predictable and tied to your data.
Modern JavaScript (Fetch)
If you, for example, want to create a fake user:
fetch("https://reqres.in/api/users", {
method: "POST",
headers: {
"Content-Type": "application/json",
"x-api-key": "YOUR_API_KEY"
},
body: JSON.stringify({
name: "paul rudd",
movies: ["I Love You Man", "Role Models"]
})
})
.then(response => response.json())
.then(data => console.log(data))
.catch(error => console.error("Error:", error));
For which the response to this request will be...
{
"name":"paul rudd",
"movies":[
"I Love You Man",
"Role Models"
],
"id":"243",
"createdAt":"2025-01-15T12:09:05.255Z"
}
You can see that the API has sent us back whatever user details we sent it, plus an id & createdAt key for our use.
Async/Await JavaScript
If you've already got your own application entities, ie. "products", you can send them in the endpoint URL, like so:
async function getProduct() {
try {
const response = await fetch("https://reqres.in/api/products/3", {
headers: {
"x-api-key": "YOUR_API_KEY"
}
});
const data = await response.json();
console.log(data);
} catch (error) {
console.error("Error:", error);
}
}
getProduct();
It would be impossible for Reqres to know your application data, so the API will respond from a sample set of Pantone colour data
{
"data":{
"id":3,
"name":"true red",
"year":2002,
"pantone_value":"19-1664"
}
}
It's entirely possible to get sample data into your interface in seconds!
Pricing plans
Free
- Validate ideas with generous free limits
- Core endpoints for prototypes
- CORS enabled for front-end integrations
- 🎯 Image to API (2 requests/day) to prove concepts fast
Pro
- Persistent backend APIs for demos and QA
- Higher endpoint limits than Free so teams can cover full journeys
- Object size limits apply (1MB each) for consistent data
- Multiple API keys for collaboration
- 🎯 AI-Powered Image to API for every new flow
Premium
- Everything in Pro plus enterprise headroom
- Higher endpoint limits than Pro for complex orgs
- Larger object limits (5MB each) for realistic datasets
- Priority support with faster response times
- 🎯 AI-Powered Image to API across the org
⚡ Stay unblocked when the free plan maxes out
Upgrade to Pro for persistent APIs, higher limits, and collaboration controls—so your demos, tests, and client projects keep running when the team leans on them most.
Upgrade nowKeep shipping even when backend resources are tapped.
ReqRes gives front-end, product, and QA teams a shared API layer that stays reliable from first mockup to production launch.
Advertising
Reach Millions of Developers. Instantly.
Your brand, job, or product could be in front of 80+ million developers and 35+ billion API requests every month. ReqRes is where the world's builders, makers, and creators come to test, learn, and launch.
Want to get your message in front of the most engaged, technical audience on the planet? Whether you're hiring, launching, or growing, there's no better place to make an impact.
Let's build something legendary together.
Perfect For Every Development Stage
Rapid Prototyping
Front-end squads turn design sign-off into live experiences the same day, keeping roadmap discussions focused on the product—not on when backend tickets will be picked up.
MVP Development
Product leaders ship MVPs with persistent data, analytics, and rate limits baked in, proving value before committing full engineering cycles.
Testing & QA
QA teams keep automated and manual tests stable with production-like responses, avoiding the flaky mocks that slow down release trains.
Learning & Demos
Educators, advocates, and solution engineers deliver compelling workshops with instant API access and realistic responses that reinforce best practices.

"We shipped a clickable prototype in a day. ReqRes handled auth, CRUD, and pagination so we could focus on the UI."
"We turned a screenshot into endpoints before a customer demo — it saved us a full sprint."